Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7428c42e29f2cc9a9a2365bfe8a7feddaef2b8dc07f9db0b96bec26f8a83c99f

Tx prefix hash: 1526942a88cfd20ed74b6ca6b394a3f166fd3e5d1865db1a6974ca7c3401468d
Tx public key: 283a43a2d39fdcf4f3625c480a09c7a97f589ae5d664688b7344b51489450b29
Timestamp: 1735609386 Timestamp [UCT]: 2024-12-31 01:43:06 Age [y:d:h:m:s]: 00:305:17:24:51
Block: 1186829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216012 RingCT/type: yes/0
Extra: 01283a43a2d39fdcf4f3625c480a09c7a97f589ae5d664688b7344b51489450b29021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aca527b8f824191ff434636d1b53eb463b863aa7a610da290db7ff5c71b84cf2 0.600000000000 1673314 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": 1186839, "vin": [ { "gen": { "height": 1186829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aca527b8f824191ff434636d1b53eb463b863aa7a610da290db7ff5c71b84cf2" } } ], "extra": [ 1, 40, 58, 67, 162, 211, 159, 220, 244, 243, 98, 92, 72, 10, 9, 199, 169, 127, 88, 154, 229, 214, 100, 104, 139, 115, 68, 181, 20, 137, 69, 11, 41, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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