Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f811dfbcee289620c7f6d2037d17a235c06aed71db5513e0c3843b8750178f4c

Tx prefix hash: 9d71f9b139877b812bead6478beb476b1f3304e9bc4a80199953ae0313164965
Tx public key: 023c17327d4e0bf2e4cd89ee089254ec98408bb355cd1b87d9045df8d6edccff
Timestamp: 1720084876 Timestamp [UCT]: 2024-07-04 09:21:16 Age [y:d:h:m:s]: 00:262:09:30:57
Block: 1058258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187473 RingCT/type: yes/0
Extra: 01023c17327d4e0bf2e4cd89ee089254ec98408bb355cd1b87d9045df8d6edccff02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19e5f5421ca65ec2d1c64fb093b8a1ea827940f17a5bbf2becfc84ca825d9aa8 0.600000000000 1528707 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": 1058268, "vin": [ { "gen": { "height": 1058258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19e5f5421ca65ec2d1c64fb093b8a1ea827940f17a5bbf2becfc84ca825d9aa8" } } ], "extra": [ 1, 2, 60, 23, 50, 125, 78, 11, 242, 228, 205, 137, 238, 8, 146, 84, 236, 152, 64, 139, 179, 85, 205, 27, 135, 217, 4, 93, 248, 214, 237, 204, 255, 2, 17, 0, 0, 0, 2, 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