Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd63a49151e2509359c6d03a7534ca0650161656ae17f8406d8283d292e4671e

Tx prefix hash: 8fac073c27fa39d6e1b9b784e33080ae802650caefa361897baf76add6a9745a
Tx public key: b1c5bc7262f595565d6002f7bcead3f0ec980f71ed61639ee0f562943f28e98f
Timestamp: 1584526875 Timestamp [UCT]: 2020-03-18 10:21:15 Age [y:d:h:m:s]: 04:342:18:11:44
Block: 84905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140354 RingCT/type: yes/0
Extra: 01b1c5bc7262f595565d6002f7bcead3f0ec980f71ed61639ee0f562943f28e98f021100000004e5e30634000000000000000000

1 output(s) for total of 321.125853839000 dcy

stealth address amount amount idx
00: 424cc1fa8ff6373a4b0cfe1ef61e8384ae9a2bfe1a981184aeb9088d31ddfe7f 321.125853839000 153683 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": 84915, "vin": [ { "gen": { "height": 84905 } } ], "vout": [ { "amount": 321125853839, "target": { "key": "424cc1fa8ff6373a4b0cfe1ef61e8384ae9a2bfe1a981184aeb9088d31ddfe7f" } } ], "extra": [ 1, 177, 197, 188, 114, 98, 245, 149, 86, 93, 96, 2, 247, 188, 234, 211, 240, 236, 152, 15, 113, 237, 97, 99, 158, 224, 245, 98, 148, 63, 40, 233, 143, 2, 17, 0, 0, 0, 4, 229, 227, 6, 52, 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