Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4fcfa733bdba628ac5230526b9f51c878a5965ad59b9a3909f575d735171a9

Tx prefix hash: 7e5a8c93bccc9c4145d72417593532af9167124064127d7ecdf9b5a7bef00897
Tx public key: b316366f7fbdee7402b728605853c0196a70121a1680f32c947ae5c562e7cab5
Timestamp: 1712185174 Timestamp [UCT]: 2024-04-03 22:59:34 Age [y:d:h:m:s]: 01:033:03:42:22
Block: 992740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284695 RingCT/type: yes/0
Extra: 01b316366f7fbdee7402b728605853c0196a70121a1680f32c947ae5c562e7cab502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1d0b33dc8182cf09f65112154425be8c3aeb46eac46b48ada75f76736ddd6c 0.600000000000 1453114 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": 992750, "vin": [ { "gen": { "height": 992740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1d0b33dc8182cf09f65112154425be8c3aeb46eac46b48ada75f76736ddd6c" } } ], "extra": [ 1, 179, 22, 54, 111, 127, 189, 238, 116, 2, 183, 40, 96, 88, 83, 192, 25, 106, 112, 18, 26, 22, 128, 243, 44, 148, 122, 229, 197, 98, 231, 202, 181, 2, 17, 0, 0, 0, 4, 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