Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc951b24cf598018c7c4aff8477dd3424d723f3bbc91e20b7c05e2b6177d04a4

Tx prefix hash: de1816611eeaf88b940d272daad0592530c877e45b800adb597987b99bbff972
Tx public key: 2995c58ddf2df48b763f7a48f7a8fdb6f90af48ecbeeb461adde9191d38567da
Timestamp: 1698433706 Timestamp [UCT]: 2023-10-27 19:08:26 Age [y:d:h:m:s]: 01:170:05:00:39
Block: 878967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382653 RingCT/type: yes/0
Extra: 012995c58ddf2df48b763f7a48f7a8fdb6f90af48ecbeeb461adde9191d38567da021100000004faf35c9c000000000000000000

1 output(s) for total of 0.750961144000 dcy

stealth address amount amount idx
00: a9f1b71b756994ff6c1cf9510c7f07e01a1e82adaafc418ae0ee67985fcd9c4c 0.750961144000 1334463 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": 878977, "vin": [ { "gen": { "height": 878967 } } ], "vout": [ { "amount": 750961144, "target": { "key": "a9f1b71b756994ff6c1cf9510c7f07e01a1e82adaafc418ae0ee67985fcd9c4c" } } ], "extra": [ 1, 41, 149, 197, 141, 223, 45, 244, 139, 118, 63, 122, 72, 247, 168, 253, 182, 249, 10, 244, 142, 203, 238, 180, 97, 173, 222, 145, 145, 211, 133, 103, 218, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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