Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ff1da2c36c4de1517785dd68f72a1450e0fd905180545e70ad62b2fad78f60c

Tx prefix hash: 763b84a254dbcdf697c0ea6d98f5186c44bfdb16fbd5fcd978a12d9a866cbeb9
Tx public key: 00d3318e07317c90227dd17f8c4480fef76ad827d51f9b65f85f1443c45b4af6
Timestamp: 1713667869 Timestamp [UCT]: 2024-04-21 02:51:09 Age [y:d:h:m:s]: 00:354:01:30:30
Block: 1005055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253121 RingCT/type: yes/0
Extra: 0100d3318e07317c90227dd17f8c4480fef76ad827d51f9b65f85f1443c45b4af60211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c40dc61101e90afdcbaea2a3f129693a6982bbb6ea791dcedbca1f2cb97882 0.600000000000 1465633 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": 1005065, "vin": [ { "gen": { "height": 1005055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c40dc61101e90afdcbaea2a3f129693a6982bbb6ea791dcedbca1f2cb97882" } } ], "extra": [ 1, 0, 211, 49, 142, 7, 49, 124, 144, 34, 125, 209, 127, 140, 68, 128, 254, 247, 106, 216, 39, 213, 31, 155, 101, 248, 95, 20, 67, 196, 91, 74, 246, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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