Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5e4d28380d45186a8d00aa5269c9155ac0959fa27233810c5acaaeded4f29d

Tx prefix hash: 0c575380efc85475e97050a2f833299d4b20d04a2c0294e4e126d54ed263d3da
Tx public key: 609564e69f0dc0b7ecd3a90c33d3b28390c9f0a2009b744daaf37fab79e1b519
Timestamp: 1727169748 Timestamp [UCT]: 2024-09-24 09:22:28 Age [y:d:h:m:s]: 00:201:20:52:37
Block: 1116994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144114 RingCT/type: yes/0
Extra: 01609564e69f0dc0b7ecd3a90c33d3b28390c9f0a2009b744daaf37fab79e1b51902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d59c4f81d2c06b46f0752e1e75737bf2b1523c57d06722156d53576d9304f747 0.600000000000 1597673 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": 1117004, "vin": [ { "gen": { "height": 1116994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d59c4f81d2c06b46f0752e1e75737bf2b1523c57d06722156d53576d9304f747" } } ], "extra": [ 1, 96, 149, 100, 230, 159, 13, 192, 183, 236, 211, 169, 12, 51, 211, 178, 131, 144, 201, 240, 162, 0, 155, 116, 77, 170, 243, 127, 171, 121, 225, 181, 25, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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