Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc05eecfcefca219f9a396a7adbea8e0dc279d991878d846d23f50b091d39bd

Tx prefix hash: a8efd3c182eb9f344f1ece2c9a111d6cdb0db8ef1e00c4b3fede136b379e01a0
Tx public key: 53aa20f9b1bad0e93967e336638b2fabaeced52bf2228f0376fe458203f91e43
Timestamp: 1729638499 Timestamp [UCT]: 2024-10-22 23:08:19 Age [y:d:h:m:s]: 00:091:15:54:45
Block: 1137432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65493 RingCT/type: yes/0
Extra: 0153aa20f9b1bad0e93967e336638b2fabaeced52bf2228f0376fe458203f91e430211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2966b3e5c990fa1e9ff6e03da9df1f1602789f59a110f90842eee93b179ecf1 0.600000000000 1620923 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": 1137442, "vin": [ { "gen": { "height": 1137432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2966b3e5c990fa1e9ff6e03da9df1f1602789f59a110f90842eee93b179ecf1" } } ], "extra": [ 1, 83, 170, 32, 249, 177, 186, 208, 233, 57, 103, 227, 54, 99, 139, 47, 171, 174, 206, 213, 43, 242, 34, 143, 3, 118, 254, 69, 130, 3, 249, 30, 67, 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