Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aae0e644255acf493d2b3f7feed75f1f48973ec3173b7857d96f85b812471f1

Tx prefix hash: f3e16713605a97c3e4144f3002a1d98cb0d6741a8c5b1ddf3bbb0e49f459a0dc
Tx public key: 05ed70c588dacf0d029e65d1af2589b63d382833e971c7c758b00c64b465c86e
Timestamp: 1712460263 Timestamp [UCT]: 2024-04-07 03:24:23 Age [y:d:h:m:s]: 01:054:02:04:08
Block: 995012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299687 RingCT/type: yes/0
Extra: 0105ed70c588dacf0d029e65d1af2589b63d382833e971c7c758b00c64b465c86e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54384cc063238cbe267fe85b4bb44bb2ab9a9238a21630f3f04198916d8104b7 0.600000000000 1455416 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": 995022, "vin": [ { "gen": { "height": 995012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54384cc063238cbe267fe85b4bb44bb2ab9a9238a21630f3f04198916d8104b7" } } ], "extra": [ 1, 5, 237, 112, 197, 136, 218, 207, 13, 2, 158, 101, 209, 175, 37, 137, 182, 61, 56, 40, 51, 233, 113, 199, 199, 88, 176, 12, 100, 180, 101, 200, 110, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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