Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1f0ee7e35bd078447b7f6119eed7adc09b809aa1d626f5ec7ca06a3a03927b

Tx prefix hash: a602a6e68bbfd59f50a57b49791e171a0328ddc440cf8211dd044cb11a585a2f
Tx public key: 1e0b5bd9f5670d8de0aa9cc481428543567dfbf0d732a19e22cc937d9107f352
Timestamp: 1741256932 Timestamp [UCT]: 2025-03-06 10:28:52 Age [y:d:h:m:s]: 00:006:07:27:26
Block: 1233333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4519 RingCT/type: yes/0
Extra: 011e0b5bd9f5670d8de0aa9cc481428543567dfbf0d732a19e22cc937d9107f3520211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 064373c09d7e348607f38486ca7dc40767454a5927e6ca5616111a73c82741d2 0.600000000000 1720252 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": 1233343, "vin": [ { "gen": { "height": 1233333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "064373c09d7e348607f38486ca7dc40767454a5927e6ca5616111a73c82741d2" } } ], "extra": [ 1, 30, 11, 91, 217, 245, 103, 13, 141, 224, 170, 156, 196, 129, 66, 133, 67, 86, 125, 251, 240, 215, 50, 161, 158, 34, 204, 147, 125, 145, 7, 243, 82, 2, 17, 0, 0, 0, 2, 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