Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7f0b8f86d98ebb28ecea530e766de40063eb72c5ce2baf969d81d7fd5b2321

Tx prefix hash: 414ff996bc02fba850cf3b6f78643cb93cb48bc1009e951ff4769317b27ec923
Tx public key: dd76e6063ff05a6963a5e410a3760be755b3731f87098d513d32b6dbb55e438a
Timestamp: 1609283623 Timestamp [UCT]: 2020-12-29 23:13:43 Age [y:d:h:m:s]: 03:313:19:41:03
Block: 171713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977005 RingCT/type: yes/0
Extra: 01dd76e6063ff05a6963a5e410a3760be755b3731f87098d513d32b6dbb55e438a0211000000f0aad74b3a000000000000000000

1 output(s) for total of 165.593853569000 dcy

stealth address amount amount idx
00: 608ab0da3daf936a2771ae4e8803ab3f2f02aa9610628fcc1734efc62a02f6b8 165.593853569000 323860 of 0

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": 171723, "vin": [ { "gen": { "height": 171713 } } ], "vout": [ { "amount": 165593853569, "target": { "key": "608ab0da3daf936a2771ae4e8803ab3f2f02aa9610628fcc1734efc62a02f6b8" } } ], "extra": [ 1, 221, 118, 230, 6, 63, 240, 90, 105, 99, 165, 228, 16, 163, 118, 11, 231, 85, 179, 115, 31, 135, 9, 141, 81, 61, 50, 182, 219, 181, 94, 67, 138, 2, 17, 0, 0, 0, 240, 170, 215, 75, 58, 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