Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6ffec9ef6f97f442d6fa2660a1e7b9f290ffdbd2d34a099b87ae7a8315e7244

Tx prefix hash: 9adb222a4e8b42926d3ace17f093de9ca451a00fd92b1d98dc993e72ba1486ac
Tx public key: 35542a47a43e900368ee3a0b38dbb9f24852b64db6c8fb5961e1e8490839b05d
Timestamp: 1706784004 Timestamp [UCT]: 2024-02-01 10:40:04 Age [y:d:h:m:s]: 01:067:00:12:57
Block: 947971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308953 RingCT/type: yes/0
Extra: 0135542a47a43e900368ee3a0b38dbb9f24852b64db6c8fb5961e1e8490839b05d0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9145632f0549071d98ad9da475f314bc15be8c6125a7981de4e217ef47ee1d9 0.600000000000 1406335 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": 947981, "vin": [ { "gen": { "height": 947971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9145632f0549071d98ad9da475f314bc15be8c6125a7981de4e217ef47ee1d9" } } ], "extra": [ 1, 53, 84, 42, 71, 164, 62, 144, 3, 104, 238, 58, 11, 56, 219, 185, 242, 72, 82, 182, 77, 182, 200, 251, 89, 97, 225, 232, 73, 8, 57, 176, 93, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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