Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954bc56048770d581fc4894ca388d90d4560047ba3a5fe04f04cc2bed64ca76f

Tx prefix hash: d1ac9d9678429ab57763c950ea3ee473d2f3cd0f09ef75d7af136257556f5a74
Tx public key: f8a517eada12685b7d21be2e743e3ba13f1f1f495e40bfd0e3df59be05662bf8
Timestamp: 1635128347 Timestamp [UCT]: 2021-10-25 02:19:07 Age [y:d:h:m:s]: 03:140:20:58:16
Block: 359885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878843 RingCT/type: yes/0
Extra: 01f8a517eada12685b7d21be2e743e3ba13f1f1f495e40bfd0e3df59be05662bf802110000001336fe6557000000000000000000

1 output(s) for total of 39.405061417000 dcy

stealth address amount amount idx
00: 179513d46d20850e07db19e864b6d39dfcef08aa8bb414334eb2b1afabd1155a 39.405061417000 732672 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": 359895, "vin": [ { "gen": { "height": 359885 } } ], "vout": [ { "amount": 39405061417, "target": { "key": "179513d46d20850e07db19e864b6d39dfcef08aa8bb414334eb2b1afabd1155a" } } ], "extra": [ 1, 248, 165, 23, 234, 218, 18, 104, 91, 125, 33, 190, 46, 116, 62, 59, 161, 63, 31, 31, 73, 94, 64, 191, 208, 227, 223, 89, 190, 5, 102, 43, 248, 2, 17, 0, 0, 0, 19, 54, 254, 101, 87, 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