Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec824eba5217c74bcd3c53bc10b621c251d64fb1b128214ac98938aa8a7a97d7

Tx prefix hash: 91f422743857bcc64dd66dfc89924aca389a18f950ec3824bf52273233ff9867
Tx public key: 0dafc49c8dcd34e59aff048fd99375438591fd2f32012b7329518c6e768be6c3
Timestamp: 1694595807 Timestamp [UCT]: 2023-09-13 09:03:27 Age [y:d:h:m:s]: 01:203:13:16:58
Block: 847122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406563 RingCT/type: yes/0
Extra: 010dafc49c8dcd34e59aff048fd99375438591fd2f32012b7329518c6e768be6c302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.957487731000 dcy

stealth address amount amount idx
00: 68a40415f8d8cffd5c2a6134f91b614086f1aadd8b7d4839f17abaf035b3f41d 0.957487731000 1300624 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": 847132, "vin": [ { "gen": { "height": 847122 } } ], "vout": [ { "amount": 957487731, "target": { "key": "68a40415f8d8cffd5c2a6134f91b614086f1aadd8b7d4839f17abaf035b3f41d" } } ], "extra": [ 1, 13, 175, 196, 156, 141, 205, 52, 229, 154, 255, 4, 143, 217, 147, 117, 67, 133, 145, 253, 47, 50, 1, 43, 115, 41, 81, 140, 110, 118, 139, 230, 195, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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