Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 156570986cef426396e399ecd347df3dd7ec26d35544308e426ade195bf0d46e

Tx prefix hash: 12a47cd2da607c266aef71d5b9c77a5dd48e038cdfc1b7fbf1c66a6730745e9f
Tx public key: 6490a098d2da9e4a6eb56c9c4359ff65dfc5c7dd2708fa712f8d41e0baf45e73
Timestamp: 1735101473 Timestamp [UCT]: 2024-12-25 04:37:53 Age [y:d:h:m:s]: 00:091:08:08:23
Block: 1182641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65041 RingCT/type: yes/0
Extra: 016490a098d2da9e4a6eb56c9c4359ff65dfc5c7dd2708fa712f8d41e0baf45e730211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163e40187fefe149e69cbcc56002d5c43c1f110430be57b71e934be9e42d4608 0.600000000000 1669076 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": 1182651, "vin": [ { "gen": { "height": 1182641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163e40187fefe149e69cbcc56002d5c43c1f110430be57b71e934be9e42d4608" } } ], "extra": [ 1, 100, 144, 160, 152, 210, 218, 158, 74, 110, 181, 108, 156, 67, 89, 255, 101, 223, 197, 199, 221, 39, 8, 250, 113, 47, 141, 65, 224, 186, 244, 94, 115, 2, 17, 0, 0, 0, 2, 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