Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b35e46d36a46b77b412997068f28fa7170c792ecbda1e3b91480e10ec2ecfa

Tx prefix hash: a924553b3818d2393773a0b2f34eaa661ec2fd3bb0be1915d800ca3da30b5faf
Tx public key: 1f300ea3dcfa88a258ae016352cc115d24c6900124917bcca0841a7ec4e925fa
Timestamp: 1690579980 Timestamp [UCT]: 2023-07-28 21:33:00 Age [y:d:h:m:s]: 01:174:10:34:19
Block: 813921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385981 RingCT/type: yes/0
Extra: 011f300ea3dcfa88a258ae016352cc115d24c6900124917bcca0841a7ec4e925fa02110000000c33af99f4000000000000000000

1 output(s) for total of 1.233507975000 dcy

stealth address amount amount idx
00: 65b5d34e7d8e48014c8a6cf83aa53c4ccb88d6fdfc52e12361617341cebe8f08 1.233507975000 1265674 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": 813931, "vin": [ { "gen": { "height": 813921 } } ], "vout": [ { "amount": 1233507975, "target": { "key": "65b5d34e7d8e48014c8a6cf83aa53c4ccb88d6fdfc52e12361617341cebe8f08" } } ], "extra": [ 1, 31, 48, 14, 163, 220, 250, 136, 162, 88, 174, 1, 99, 82, 204, 17, 93, 36, 198, 144, 1, 36, 145, 123, 204, 160, 132, 26, 126, 196, 233, 37, 250, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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