Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1034184f2fffc072c1faf0d33c3f85200544ae5e5e4076606691a44ee92a345

Tx prefix hash: 8ffe19019dac175145bf2feca87c066177d4222096c35f9cb8998cf856b5ccbb
Tx public key: 6856a1fef8d1758aac8a20f8bce5fdae4138dc584f7a97b5fd5832a25b8f222d
Timestamp: 1738560565 Timestamp [UCT]: 2025-02-03 05:29:25 Age [y:d:h:m:s]: 00:291:09:11:41
Block: 1210986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206027 RingCT/type: yes/0
Extra: 016856a1fef8d1758aac8a20f8bce5fdae4138dc584f7a97b5fd5832a25b8f222d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61f0dd0ccd936a41e3481c06decf0f45a6af438156ae81360569561d465428e0 0.600000000000 1697741 of 15

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": 1210996, "vin": [ { "gen": { "height": 1210986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61f0dd0ccd936a41e3481c06decf0f45a6af438156ae81360569561d465428e0" } } ], "extra": [ 1, 104, 86, 161, 254, 248, 209, 117, 138, 172, 138, 32, 248, 188, 229, 253, 174, 65, 56, 220, 88, 79, 122, 151, 181, 253, 88, 50, 162, 91, 143, 34, 45, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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