Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b1d3699f4c27250bf07722b0cf81b7d4fa4f1108e01cc6858ba14a2b0bd893

Tx prefix hash: 1a0b8b40c485a4786d13b080bd9ccf3f864eafb889ccbce6d5eccf5204e19cb5
Tx public key: dc26afa44f3b083b2d334945b3a1936e7672e515cd40509603d5dccdb0b9abb2
Timestamp: 1670245999 Timestamp [UCT]: 2022-12-05 13:13:19 Age [y:d:h:m:s]: 02:147:02:31:26
Block: 645979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626832 RingCT/type: yes/0
Extra: 01dc26afa44f3b083b2d334945b3a1936e7672e515cd40509603d5dccdb0b9abb202110000000183600029000000000000000000

1 output(s) for total of 4.442254201000 dcy

stealth address amount amount idx
00: b240ce45e123f301da902e6ac76d39657b03f6bc4d6d97eefa586aefb3aa5f52 4.442254201000 1086180 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": 645989, "vin": [ { "gen": { "height": 645979 } } ], "vout": [ { "amount": 4442254201, "target": { "key": "b240ce45e123f301da902e6ac76d39657b03f6bc4d6d97eefa586aefb3aa5f52" } } ], "extra": [ 1, 220, 38, 175, 164, 79, 59, 8, 59, 45, 51, 73, 69, 179, 161, 147, 110, 118, 114, 229, 21, 205, 64, 80, 150, 3, 213, 220, 205, 176, 185, 171, 178, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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