Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01f28147ff0e36f5f1854b3353e676dda987a5ef994b7d2c8dacb724cdf522e

Tx prefix hash: b1ffb9356e1a2c3bdb417fe6aa242439cbdbc1f4627c1fbe3eb73b0bd988484c
Tx public key: 27d47db6a4d06c7558727d42d38eecc8ebb51e3965d6285c513550860928646a
Timestamp: 1710452992 Timestamp [UCT]: 2024-03-14 21:49:52 Age [y:d:h:m:s]: 01:039:08:47:37
Block: 978422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289110 RingCT/type: yes/0
Extra: 0127d47db6a4d06c7558727d42d38eecc8ebb51e3965d6285c513550860928646a02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bda2166a3b81e773e2eade1934cd1cf31e00fd4cb44b69358a8e3e9a9d9043d8 0.600000000000 1438449 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": 978432, "vin": [ { "gen": { "height": 978422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bda2166a3b81e773e2eade1934cd1cf31e00fd4cb44b69358a8e3e9a9d9043d8" } } ], "extra": [ 1, 39, 212, 125, 182, 164, 208, 108, 117, 88, 114, 125, 66, 211, 142, 236, 200, 235, 181, 30, 57, 101, 214, 40, 92, 81, 53, 80, 134, 9, 40, 100, 106, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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