Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c069484fb7579b52214cfc505959a52730e49f225ae9105d1d9f7e131b52e533

Tx prefix hash: e0b74f3ef24a152ead7510bb31c80a54340b54b085d7eae33f8c0bc20ae1b1a0
Tx public key: e4bc75a18672470099c9ab978ae54e73d15e6f12a77e47e989c3c5a927ca684a
Timestamp: 1720370416 Timestamp [UCT]: 2024-07-07 16:40:16 Age [y:d:h:m:s]: 00:346:01:50:12
Block: 1060623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247204 RingCT/type: yes/0
Extra: 01e4bc75a18672470099c9ab978ae54e73d15e6f12a77e47e989c3c5a927ca684a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb51ba6e38c00fb40293cac946f9ee607c08af8ad80e93284f1d2835a7945b4f 0.600000000000 1531108 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": 1060633, "vin": [ { "gen": { "height": 1060623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb51ba6e38c00fb40293cac946f9ee607c08af8ad80e93284f1d2835a7945b4f" } } ], "extra": [ 1, 228, 188, 117, 161, 134, 114, 71, 0, 153, 201, 171, 151, 138, 229, 78, 115, 209, 94, 111, 18, 167, 126, 71, 233, 137, 195, 197, 169, 39, 202, 104, 74, 2, 17, 0, 0, 0, 6, 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