Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31c51585288175659d3aaba803d7542f061f6475a4440477f27a25a0b106b08

Tx prefix hash: 9cbb4e3a559e9689fa9e8dc723af4fc1a9444f3b6aba1daf8f6e6c3182fd096d
Tx public key: 33ca792f7be5901b5413c519095adb9730d74a65b7ab118f56683fabd823e935
Timestamp: 1625398548 Timestamp [UCT]: 2021-07-04 11:35:48 Age [y:d:h:m:s]: 03:189:10:32:09
Block: 288117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 905042 RingCT/type: yes/0
Extra: 0133ca792f7be5901b5413c519095adb9730d74a65b7ab118f56683fabd823e93502110000000e694a138f000000000000000000

1 output(s) for total of 68.131709134000 dcy

stealth address amount amount idx
00: 1a99ff10a6f550bfe3b5280d03c6a46fc5607fd00d4266a920dac408157394d8 68.131709134000 603680 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": 288127, "vin": [ { "gen": { "height": 288117 } } ], "vout": [ { "amount": 68131709134, "target": { "key": "1a99ff10a6f550bfe3b5280d03c6a46fc5607fd00d4266a920dac408157394d8" } } ], "extra": [ 1, 51, 202, 121, 47, 123, 229, 144, 27, 84, 19, 197, 25, 9, 90, 219, 151, 48, 215, 74, 101, 183, 171, 17, 143, 86, 104, 63, 171, 216, 35, 233, 53, 2, 17, 0, 0, 0, 14, 105, 74, 19, 143, 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