Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597195c41451856f229a5a70e3f20d6b733a1fdb0ff16550fd691a594962082e

Tx prefix hash: 51767a40b225f6cf48f0ab0b4c13cc6396b4b032b9c1eaa98e3600562436f077
Tx public key: 2e78a435b2e2ded6578fc0d503d198bd4da131597c40b17084f1d831873369ad
Timestamp: 1737116889 Timestamp [UCT]: 2025-01-17 12:28:09 Age [y:d:h:m:s]: 00:154:23:37:21
Block: 1199309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110429 RingCT/type: yes/0
Extra: 012e78a435b2e2ded6578fc0d503d198bd4da131597c40b17084f1d831873369ad021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3beaeff4c852c8665e6eb207d2dea053692eae2df86632e9799d195d7f77fcc7 0.600000000000 1685940 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": 1199319, "vin": [ { "gen": { "height": 1199309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3beaeff4c852c8665e6eb207d2dea053692eae2df86632e9799d195d7f77fcc7" } } ], "extra": [ 1, 46, 120, 164, 53, 178, 226, 222, 214, 87, 143, 192, 213, 3, 209, 152, 189, 77, 161, 49, 89, 124, 64, 177, 112, 132, 241, 216, 49, 135, 51, 105, 173, 2, 17, 0, 0, 0, 5, 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