Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f78145a68cc06e9f7fa1f1826a6d2150900d6d4378ea265591183d22f3621547

Tx prefix hash: d365af3de2ad8201b8db10f1cd35a233bdd1ba7ec09610e5bbecd283bc9be3f9
Tx public key: 1e419be690f3df9e24fd06388cf4b9109592bf33f85a3e6164827f79f1bce0ff
Timestamp: 1729385127 Timestamp [UCT]: 2024-10-20 00:45:27 Age [y:d:h:m:s]: 00:156:10:38:08
Block: 1135354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111582 RingCT/type: yes/0
Extra: 011e419be690f3df9e24fd06388cf4b9109592bf33f85a3e6164827f79f1bce0ff021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f746d9dcf8789e38f99fbb6e11452c02d7c211b50ec2821be18581f6fb73be8 0.600000000000 1618691 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": 1135364, "vin": [ { "gen": { "height": 1135354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f746d9dcf8789e38f99fbb6e11452c02d7c211b50ec2821be18581f6fb73be8" } } ], "extra": [ 1, 30, 65, 155, 230, 144, 243, 223, 158, 36, 253, 6, 56, 140, 244, 185, 16, 149, 146, 191, 51, 248, 90, 62, 97, 100, 130, 127, 121, 241, 188, 224, 255, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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