Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e5bb419a62e975f8dcc0d882350b85d04767ef2932f1a10269472292e2f25ba

Tx prefix hash: 61700ec05e186b60e978dcc85c05ed785f3c3c5695c9feaf5c035f6f8535b037
Tx public key: 75ea76271d65e07976178f86fee51eda9419351eecc345d31df6b081f518087d
Timestamp: 1681717173 Timestamp [UCT]: 2023-04-17 07:39:33 Age [y:d:h:m:s]: 01:312:18:31:41
Block: 740408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484784 RingCT/type: yes/0
Extra: 0175ea76271d65e07976178f86fee51eda9419351eecc345d31df6b081f518087d02110000000475e3f0e9000000000000000000

1 output(s) for total of 2.161330366000 dcy

stealth address amount amount idx
00: f9418ffffa9a3c071fbb55d0e93c7119bb7cb7a8c997fbbd450000eac04982c1 2.161330366000 1187303 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": 740418, "vin": [ { "gen": { "height": 740408 } } ], "vout": [ { "amount": 2161330366, "target": { "key": "f9418ffffa9a3c071fbb55d0e93c7119bb7cb7a8c997fbbd450000eac04982c1" } } ], "extra": [ 1, 117, 234, 118, 39, 29, 101, 224, 121, 118, 23, 143, 134, 254, 229, 30, 218, 148, 25, 53, 30, 236, 195, 69, 211, 29, 246, 176, 129, 245, 24, 8, 125, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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