Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f7cc39878b28060b3cabcb5b19c9f8bf2270bb875e4a1294162350053d4401

Tx prefix hash: cdfc5410c16e613e8b8ab9de1e9b97d11f24d97451fd4d74dc2103c5e133a344
Tx public key: 709e1c065e14d0c881b9406e1a7d6113cb7cbf033b985edf20a45593156645f2
Timestamp: 1634303790 Timestamp [UCT]: 2021-10-15 13:16:30 Age [y:d:h:m:s]: 03:194:19:21:14
Block: 353587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 916875 RingCT/type: yes/0
Extra: 01709e1c065e14d0c881b9406e1a7d6113cb7cbf033b985edf20a45593156645f20211000000045d7cc334000000000000000000

1 output(s) for total of 41.344705844000 dcy

stealth address amount amount idx
00: a0a0aa4c9e7e7fd392021a0a163a035eddac7accb5edd9472543f382cf5c94fa 41.344705844000 722503 of 0

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": 353597, "vin": [ { "gen": { "height": 353587 } } ], "vout": [ { "amount": 41344705844, "target": { "key": "a0a0aa4c9e7e7fd392021a0a163a035eddac7accb5edd9472543f382cf5c94fa" } } ], "extra": [ 1, 112, 158, 28, 6, 94, 20, 208, 200, 129, 185, 64, 110, 26, 125, 97, 19, 203, 124, 191, 3, 59, 152, 94, 223, 32, 164, 85, 147, 21, 102, 69, 242, 2, 17, 0, 0, 0, 4, 93, 124, 195, 52, 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