Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3499db9f810a3b62f9dc14f80c13732cabc05a6a75657275e796b0a73a6bf497

Tx prefix hash: 4fa4c068052e574d8965cab6123c571d1f7af272120b9d9c14f7ae26ac2b5a27
Tx public key: fce536033eb6ea31f282d4f2bc04bee5ae9d938af9c2d26df4d278ec790e576a
Timestamp: 1722760563 Timestamp [UCT]: 2024-08-04 08:36:03 Age [y:d:h:m:s]: 01:095:03:44:32
Block: 1080435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326491 RingCT/type: yes/0
Extra: 01fce536033eb6ea31f282d4f2bc04bee5ae9d938af9c2d26df4d278ec790e576a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926879178bbcb61e4d27dc04a6122ebbfd69d4ae866a0c19a641bf53198c1c68 0.600000000000 1553790 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": 1080445, "vin": [ { "gen": { "height": 1080435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926879178bbcb61e4d27dc04a6122ebbfd69d4ae866a0c19a641bf53198c1c68" } } ], "extra": [ 1, 252, 229, 54, 3, 62, 182, 234, 49, 242, 130, 212, 242, 188, 4, 190, 229, 174, 157, 147, 138, 249, 194, 210, 109, 244, 210, 120, 236, 121, 14, 87, 106, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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