Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f9ef65d195ef3ebd1d7551d356684f8a3e9f1d017d201ac8fc1365d2023373

Tx prefix hash: 03fe645e1442ea28b1adffe48e84e4af0155f2e02ed606d2ca5b17c2791047c3
Tx public key: 4ec692b786efbba3802e9c624a881b38f5b0316604664a2d0fe2d8048dbd2374
Timestamp: 1710842783 Timestamp [UCT]: 2024-03-19 10:06:23 Age [y:d:h:m:s]: 00:313:20:32:34
Block: 981655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224409 RingCT/type: yes/0
Extra: 014ec692b786efbba3802e9c624a881b38f5b0316604664a2d0fe2d8048dbd237402110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eba1f9acd03a2146bcd578cbb01ec2ab5a80a76aa088fa7d726f019fdae445a 0.600000000000 1441752 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": 981665, "vin": [ { "gen": { "height": 981655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eba1f9acd03a2146bcd578cbb01ec2ab5a80a76aa088fa7d726f019fdae445a" } } ], "extra": [ 1, 78, 198, 146, 183, 134, 239, 187, 163, 128, 46, 156, 98, 74, 136, 27, 56, 245, 176, 49, 102, 4, 102, 74, 45, 15, 226, 216, 4, 141, 189, 35, 116, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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