Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a91d6de85ea08de77f2757a0c1c3a452a80864774efd11bff9d2750ac7c05d3

Tx prefix hash: 9b17da209d7be1b80231dcd1f1ea3282aa53ef770065fa6bff9a2d14a9475ac0
Tx public key: cdd932fdd0267cd52e6ad6ec2a0c418fd8ffc5d13512f881f77df3a8a5089ddb
Timestamp: 1734738851 Timestamp [UCT]: 2024-12-20 23:54:11 Age [y:d:h:m:s]: 00:178:19:27:06
Block: 1179657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127493 RingCT/type: yes/0
Extra: 01cdd932fdd0267cd52e6ad6ec2a0c418fd8ffc5d13512f881f77df3a8a5089ddb0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97dd92a4805979a068d7b6c400a7a75bd0cd368b088cc86e96747b84ee298580 0.600000000000 1666056 of 15

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": 1179667, "vin": [ { "gen": { "height": 1179657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97dd92a4805979a068d7b6c400a7a75bd0cd368b088cc86e96747b84ee298580" } } ], "extra": [ 1, 205, 217, 50, 253, 208, 38, 124, 213, 46, 106, 214, 236, 42, 12, 65, 143, 216, 255, 197, 209, 53, 18, 248, 129, 247, 125, 243, 168, 165, 8, 157, 219, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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