Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 666cff001da54ac7f60ca61813eac84cd71c65d6d12e4bdce7bc9b1b8983d0db

Tx prefix hash: a6fd6961f1c60fc6f24adfce57070360b3957e9853d679a01c42834bfb50d693
Tx public key: b069480aa9b969e47a1ddaedc73fc7a0e9e3908defb2b6b166cfe1dec5d6d98e
Timestamp: 1737630193 Timestamp [UCT]: 2025-01-23 11:03:13 Age [y:d:h:m:s]: 00:148:23:19:03
Block: 1203518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106169 RingCT/type: yes/0
Extra: 01b069480aa9b969e47a1ddaedc73fc7a0e9e3908defb2b6b166cfe1dec5d6d98e0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c36a83bc319ed6575cec5111c2fb63925b46c327158dd572601cbff1da37656 0.600000000000 1690195 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": 1203528, "vin": [ { "gen": { "height": 1203518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c36a83bc319ed6575cec5111c2fb63925b46c327158dd572601cbff1da37656" } } ], "extra": [ 1, 176, 105, 72, 10, 169, 185, 105, 228, 122, 29, 218, 237, 199, 63, 199, 160, 233, 227, 144, 141, 239, 178, 182, 177, 102, 207, 225, 222, 197, 214, 217, 142, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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