Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373f272e934afe4303e51d1749049124a7bce0274b1cf131e254393c37ff59c6

Tx prefix hash: 75ba72b828bf7b1645ce62e5e1708a860f564dfe3ce5f705a3cd59cf8c83877f
Tx public key: f886fa2ebf10b5cc0389a9495ff75746c6a20cd13e6b550c47b82df48903f4a1
Timestamp: 1707639597 Timestamp [UCT]: 2024-02-11 08:19:57 Age [y:d:h:m:s]: 01:083:19:06:39
Block: 955070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320954 RingCT/type: yes/0
Extra: 01f886fa2ebf10b5cc0389a9495ff75746c6a20cd13e6b550c47b82df48903f4a10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d097aa6f33ab15163f1a8dad4d2264b47e1fe7a8f99f684e5ca665c80692e6 0.600000000000 1414352 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": 955080, "vin": [ { "gen": { "height": 955070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d097aa6f33ab15163f1a8dad4d2264b47e1fe7a8f99f684e5ca665c80692e6" } } ], "extra": [ 1, 248, 134, 250, 46, 191, 16, 181, 204, 3, 137, 169, 73, 95, 247, 87, 70, 198, 162, 12, 209, 62, 107, 85, 12, 71, 184, 45, 244, 137, 3, 244, 161, 2, 17, 0, 0, 0, 1, 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