Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3b6d5601f2ebfa8ce6361afa6deff8ace366a18c73053b5e3b219bb2c52eb723

Tx prefix hash: d9fe3aaf7cddd4265293892be21c04da670425beec7688c2d002c71a64672dd4
Tx public key: 61ee6afd53b852a2ca24c06f1d9a07b450ab1f768bb6b7cf32b196732881704f
Timestamp: 1673126762 Timestamp [UCT]: 2023-01-07 21:26:02 Age [y:d:h:m:s]: 02:125:05:45:20
Block: 669814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611204 RingCT/type: yes/0
Extra: 0161ee6afd53b852a2ca24c06f1d9a07b450ab1f768bb6b7cf32b196732881704f02110000000252542ceb000000000000000000

1 output(s) for total of 3.703634513000 dcy

stealth address amount amount idx
00: 34f7dd423a5b0e9bea3dd82e2d8d4ca9782bba624a31cf3f1eeebaa6ba260abd 3.703634513000 1111175 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 669824, "vin": [ { "gen": { "height": 669814 } } ], "vout": [ { "amount": 3703634513, "target": { "key": "34f7dd423a5b0e9bea3dd82e2d8d4ca9782bba624a31cf3f1eeebaa6ba260abd" } } ], "extra": [ 1, 97, 238, 106, 253, 83, 184, 82, 162, 202, 36, 192, 111, 29, 154, 7, 180, 80, 171, 31, 118, 139, 182, 183, 207, 50, 177, 150, 115, 40, 129, 112, 79, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8