Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59cd5a978035372eaaf3eca4e576f86022e35b8a2b4169ae028f9a6460ff2479

Tx prefix hash: b33f0d5573df4b85b23394a49829874239d9b78a13163ea61655b6a045ce5a10
Tx public key: 83512e119fbdbeda91b77903e002e63f550bee8d3f46a88d23f8a01f067a2b96
Timestamp: 1715511757 Timestamp [UCT]: 2024-05-12 11:02:37 Age [y:d:h:m:s]: 00:307:12:15:43
Block: 1020379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219794 RingCT/type: yes/0
Extra: 0183512e119fbdbeda91b77903e002e63f550bee8d3f46a88d23f8a01f067a2b9602110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803a09f641b069db151351fe8d04e5b3f4eeddc3f345f5da175bcd770026a29f 0.600000000000 1484444 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": 1020389, "vin": [ { "gen": { "height": 1020379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803a09f641b069db151351fe8d04e5b3f4eeddc3f345f5da175bcd770026a29f" } } ], "extra": [ 1, 131, 81, 46, 17, 159, 189, 190, 218, 145, 183, 121, 3, 224, 2, 230, 63, 85, 11, 238, 141, 63, 70, 168, 141, 35, 248, 160, 31, 6, 122, 43, 150, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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