Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1afc774e5008811dbde1d4cf8d37df4c0aa2ed94bbdfcd7b5fc7c0fa42f5fc

Tx prefix hash: e984e772b690035152ccefe9368a7c17f06ea7d581f5f399b35a9876a54c035b
Tx public key: add45df7829f858a8bddf82203fd767389ee6f2704737cc75d2395730a4cf88b
Timestamp: 1716752439 Timestamp [UCT]: 2024-05-26 19:40:39 Age [y:d:h:m:s]: 00:157:19:46:26
Block: 1030647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112955 RingCT/type: yes/0
Extra: 01add45df7829f858a8bddf82203fd767389ee6f2704737cc75d2395730a4cf88b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0c3f5691cafd0a8e62ac06d375aa324e1b3d2ba097ff378eecdc17743b891a 0.600000000000 1498904 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": 1030657, "vin": [ { "gen": { "height": 1030647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0c3f5691cafd0a8e62ac06d375aa324e1b3d2ba097ff378eecdc17743b891a" } } ], "extra": [ 1, 173, 212, 93, 247, 130, 159, 133, 138, 139, 221, 248, 34, 3, 253, 118, 115, 137, 238, 111, 39, 4, 115, 124, 199, 93, 35, 149, 115, 10, 76, 248, 139, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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