Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e05532a6571be3dd03e28b6253c4714ae7aad5ff4fcd5dff5c840921b66fed8

Tx prefix hash: edc143e73fe6b9894d771973a2364bf2be141e28baf4c8fcc3f30b6971dc2729
Tx public key: 67e15007b576d8b29e992e51de4d67a66038c7c9f813c4c28091eb2806c893b5
Timestamp: 1737487304 Timestamp [UCT]: 2025-01-21 19:21:44 Age [y:d:h:m:s]: 00:148:19:30:29
Block: 1202336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106100 RingCT/type: yes/0
Extra: 0167e15007b576d8b29e992e51de4d67a66038c7c9f813c4c28091eb2806c893b50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7522cb78e5911fa24c0e75982bad29a85ce70985f4c4d4980c632e0bd2146da3 0.600000000000 1688999 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": 1202346, "vin": [ { "gen": { "height": 1202336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7522cb78e5911fa24c0e75982bad29a85ce70985f4c4d4980c632e0bd2146da3" } } ], "extra": [ 1, 103, 225, 80, 7, 181, 118, 216, 178, 158, 153, 46, 81, 222, 77, 103, 166, 96, 56, 199, 201, 248, 19, 196, 194, 128, 145, 235, 40, 6, 200, 147, 181, 2, 17, 0, 0, 0, 1, 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