Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c92fbcc21d76a13bd45cb38861953e62eb6ffb31d29875f2188fc88a97fb2f18

Tx prefix hash: d3efbd0fc1cee6071dd606dc3656ec49a535dde7f8696cab33ebeddda921eef9
Tx public key: 4a39a2c6d747e14b76404f7f0a2c8f53bc88c1e745c1e9b8aaad4c12798251a8
Timestamp: 1736938265 Timestamp [UCT]: 2025-01-15 10:51:05 Age [y:d:h:m:s]: 00:155:14:36:10
Block: 1197826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110904 RingCT/type: yes/0
Extra: 014a39a2c6d747e14b76404f7f0a2c8f53bc88c1e745c1e9b8aaad4c12798251a80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6df76ddb5463208015191705e673eb57224a60a8df12b673f76314126c489412 0.600000000000 1684443 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": 1197836, "vin": [ { "gen": { "height": 1197826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6df76ddb5463208015191705e673eb57224a60a8df12b673f76314126c489412" } } ], "extra": [ 1, 74, 57, 162, 198, 215, 71, 225, 75, 118, 64, 79, 127, 10, 44, 143, 83, 188, 136, 193, 231, 69, 193, 233, 184, 170, 173, 76, 18, 121, 130, 81, 168, 2, 17, 0, 0, 0, 4, 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