Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2067961aa3b891f81a98c187bec047f5caf2e377991df3e1ca89c2b5e635587

Tx prefix hash: 3cdc83445c5f9a23fc2104d47901eb73cb52da49aa8f178583da8ecc63722de9
Tx public key: 0ee993db205cf8fb009e003b142f472fb6fffbdd79b858f7667a9449e6e15045
Timestamp: 1699810479 Timestamp [UCT]: 2023-11-12 17:34:39 Age [y:d:h:m:s]: 02:056:20:17:41
Block: 890181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560475 RingCT/type: yes/0
Extra: 010ee993db205cf8fb009e003b142f472fb6fffbdd79b858f7667a9449e6e1504502110000001075e3f0e9000000000000000000

1 output(s) for total of 0.689383386000 dcy

stealth address amount amount idx
00: 6f377c02cbc66a0cbbd604f6b65a0e4839a42e23f11e06173ed9683d97ad68a2 0.689383386000 1346202 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": 890191, "vin": [ { "gen": { "height": 890181 } } ], "vout": [ { "amount": 689383386, "target": { "key": "6f377c02cbc66a0cbbd604f6b65a0e4839a42e23f11e06173ed9683d97ad68a2" } } ], "extra": [ 1, 14, 233, 147, 219, 32, 92, 248, 251, 0, 158, 0, 59, 20, 47, 71, 47, 182, 255, 251, 221, 121, 184, 88, 247, 102, 122, 148, 73, 230, 225, 80, 69, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 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