Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f26415b67cf4f481eb65e1662c667a633ce669fd015e451a80a658c796f4b4e

Tx prefix hash: f99f4ec54a2ad9ba26da7f2eee65abd398f30cdc670ce0ca18ea088cf6d1ce52
Tx public key: 734387b1f2e87bb5fa7030ff3559f1882fd3d64da3ae884a31573fb15ee3c945
Timestamp: 1712187029 Timestamp [UCT]: 2024-04-03 23:30:29 Age [y:d:h:m:s]: 00:280:05:32:07
Block: 992752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200618 RingCT/type: yes/0
Extra: 01734387b1f2e87bb5fa7030ff3559f1882fd3d64da3ae884a31573fb15ee3c94502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3534cbef7c867f8894d44ed7e4778377e6a488e563741fe20529310a99a275b 0.600000000000 1453126 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": 992762, "vin": [ { "gen": { "height": 992752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3534cbef7c867f8894d44ed7e4778377e6a488e563741fe20529310a99a275b" } } ], "extra": [ 1, 115, 67, 135, 177, 242, 232, 123, 181, 250, 112, 48, 255, 53, 89, 241, 136, 47, 211, 214, 77, 163, 174, 136, 74, 49, 87, 63, 177, 94, 227, 201, 69, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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