Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f35e1cd3503af23bc20e97a80137ad3f0c2770622fb37430b0c5c13f54062a

Tx prefix hash: bb3b0daa3c77c0d4bc18418869d19e7892389f5662b7a531b12c5f2b04cea322
Tx public key: 080e9d49f3c0b8472b729aa72f814ce00f36f4679d2201827d34a11a9c4a8233
Timestamp: 1712660650 Timestamp [UCT]: 2024-04-09 11:04:10 Age [y:d:h:m:s]: 00:314:14:31:17
Block: 996692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224891 RingCT/type: yes/0
Extra: 01080e9d49f3c0b8472b729aa72f814ce00f36f4679d2201827d34a11a9c4a82330211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5efe4c9bff1bdb5e53eec253d76221fb605c0eda648ea542c102672f5a56a9e5 0.600000000000 1457118 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": 996702, "vin": [ { "gen": { "height": 996692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5efe4c9bff1bdb5e53eec253d76221fb605c0eda648ea542c102672f5a56a9e5" } } ], "extra": [ 1, 8, 14, 157, 73, 243, 192, 184, 71, 43, 114, 154, 167, 47, 129, 76, 224, 15, 54, 244, 103, 157, 34, 1, 130, 125, 52, 161, 26, 156, 74, 130, 51, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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