Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd89544c0f30c6e4328714ee8802333391a2790d76313900772d4dc67247ed81

Tx prefix hash: 79494a62286fda4f5c816360607a841011f089bfe0163899ca28ef94f625add6
Tx public key: 8c6cbf45a4eae9c67baf05e8d249ea9c55b3d22d55d3976695c820a53b381472
Timestamp: 1650378643 Timestamp [UCT]: 2022-04-19 14:30:43 Age [y:d:h:m:s]: 02:251:03:39:52
Block: 483634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699406 RingCT/type: yes/0
Extra: 018c6cbf45a4eae9c67baf05e8d249ea9c55b3d22d55d3976695c820a53b381472021100000002e6d27f9c000000000000000000

1 output(s) for total of 15.329218742000 dcy

stealth address amount amount idx
00: 364dbe026497a8c39e98c998ece8386684c81fc8746f110f12a1976591eb4175 15.329218742000 905351 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": 483644, "vin": [ { "gen": { "height": 483634 } } ], "vout": [ { "amount": 15329218742, "target": { "key": "364dbe026497a8c39e98c998ece8386684c81fc8746f110f12a1976591eb4175" } } ], "extra": [ 1, 140, 108, 191, 69, 164, 234, 233, 198, 123, 175, 5, 232, 210, 73, 234, 156, 85, 179, 210, 45, 85, 211, 151, 102, 149, 200, 32, 165, 59, 56, 20, 114, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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