Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d88e1c4372f316f4cb4e1b6df2e25c5c8b288692f37eb37ad0a5f4a7713607

Tx prefix hash: f58bab97f55a246675daa337ae11221ecdb08d7eb7976c3b9178f845e7142dbe
Tx public key: 8c10c2ba89e5b83c00bd5e0e93cb6a13af9f5f6a60eb8894de57d0e7de2a88f0
Timestamp: 1706471558 Timestamp [UCT]: 2024-01-28 19:52:38 Age [y:d:h:m:s]: 01:069:07:17:40
Block: 945376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310600 RingCT/type: yes/0
Extra: 018c10c2ba89e5b83c00bd5e0e93cb6a13af9f5f6a60eb8894de57d0e7de2a88f00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3839c0b2771703976b54b8f552c2db5bfc819227380ac08d3a529fa1025c931 0.600000000000 1403688 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": 945386, "vin": [ { "gen": { "height": 945376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3839c0b2771703976b54b8f552c2db5bfc819227380ac08d3a529fa1025c931" } } ], "extra": [ 1, 140, 16, 194, 186, 137, 229, 184, 60, 0, 189, 94, 14, 147, 203, 106, 19, 175, 159, 95, 106, 96, 235, 136, 148, 222, 87, 208, 231, 222, 42, 136, 240, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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