Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c7077509a9809fc6f59f6d00c2ebd1cfc4567c43dc5cb90fddf5fa2ab217bd

Tx prefix hash: 2cd8077f19040ed872e64795e036f15468fcf3edb8b72d7129566930548ad4a6
Tx public key: 1d70297d1cdcc27477b5d2f10db13223a2beeccbd283c2fecb471a3c5dc24547
Timestamp: 1734498246 Timestamp [UCT]: 2024-12-18 05:04:06 Age [y:d:h:m:s]: 00:178:13:43:09
Block: 1177671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127347 RingCT/type: yes/0
Extra: 011d70297d1cdcc27477b5d2f10db13223a2beeccbd283c2fecb471a3c5dc2454702110000000139ec141b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dcb93300b3d62f440f75e8a9feaccbae0fbdd0a5a4dcb830f1de84ca19d457a 0.600000000000 1664044 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": 1177681, "vin": [ { "gen": { "height": 1177671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dcb93300b3d62f440f75e8a9feaccbae0fbdd0a5a4dcb830f1de84ca19d457a" } } ], "extra": [ 1, 29, 112, 41, 125, 28, 220, 194, 116, 119, 181, 210, 241, 13, 177, 50, 35, 162, 190, 236, 203, 210, 131, 194, 254, 203, 71, 26, 60, 93, 194, 69, 71, 2, 17, 0, 0, 0, 1, 57, 236, 20, 27, 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