Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a2aea34aa7f19e350165c67d9b41839fc8b771b3325a40948003d330293a39c

Tx prefix hash: 323889ebd7aaa8658649bda91cf80db07ecae10bb0eb3090d89f2aef37ebd843
Tx public key: 00d1186878a28a16bb9684f3f019b114aecdd1b825f2555909bd50a8dcb56db0
Timestamp: 1698084538 Timestamp [UCT]: 2023-10-23 18:08:58 Age [y:d:h:m:s]: 01:090:13:20:22
Block: 876070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325916 RingCT/type: yes/0
Extra: 0100d1186878a28a16bb9684f3f019b114aecdd1b825f2555909bd50a8dcb56db002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.767744006000 dcy

stealth address amount amount idx
00: 03009936bb68f74fbedb477f56ccc76fd28f1927b8d9d1bf611db3ae7f8136e2 0.767744006000 1331380 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": 876080, "vin": [ { "gen": { "height": 876070 } } ], "vout": [ { "amount": 767744006, "target": { "key": "03009936bb68f74fbedb477f56ccc76fd28f1927b8d9d1bf611db3ae7f8136e2" } } ], "extra": [ 1, 0, 209, 24, 104, 120, 162, 138, 22, 187, 150, 132, 243, 240, 25, 177, 20, 174, 205, 209, 184, 37, 242, 85, 89, 9, 189, 80, 168, 220, 181, 109, 176, 2, 17, 0, 0, 0, 3, 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