Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c13bfa5372134fdad46b0500453552ce3be7c8d5314216bb71a1d18566f317d

Tx prefix hash: 6b446761cc9c40262bc2fd47c3b52b5dd0fc6f775e11a156479ad3518c1d37b5
Tx public key: 61dd258834afb693744c7ee48f36ae533a0ba4a19b3a513377c3537c838a90a4
Timestamp: 1734274375 Timestamp [UCT]: 2024-12-15 14:52:55 Age [y:d:h:m:s]: 00:188:15:43:36
Block: 1175806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134477 RingCT/type: yes/0
Extra: 0161dd258834afb693744c7ee48f36ae533a0ba4a19b3a513377c3537c838a90a40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38e030c1c634754f9145d2651c72b504dc097c4b0f463fa8c3d9cf66c44f85c5 0.600000000000 1662131 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": 1175816, "vin": [ { "gen": { "height": 1175806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38e030c1c634754f9145d2651c72b504dc097c4b0f463fa8c3d9cf66c44f85c5" } } ], "extra": [ 1, 97, 221, 37, 136, 52, 175, 182, 147, 116, 76, 126, 228, 143, 54, 174, 83, 58, 11, 164, 161, 155, 58, 81, 51, 119, 195, 83, 124, 131, 138, 144, 164, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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