Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28fc65e463b3099aa16b21a57eeeda9c76fd74f5b75b6d50948b5c85a64a5b95

Tx prefix hash: 2715bb85551135d97113bdcd1bbd8cbe61fa7508809b3c6e3e7fd25b1177c1a8
Tx public key: 1497bbdd7a03b9047a1d63d7333751775975b18143d05a05c5d035a4563816a1
Timestamp: 1732109977 Timestamp [UCT]: 2024-11-20 13:39:37 Age [y:d:h:m:s]: 00:157:02:17:24
Block: 1157849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112118 RingCT/type: yes/0
Extra: 011497bbdd7a03b9047a1d63d7333751775975b18143d05a05c5d035a4563816a10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e1249f0a06608a69b2a198c1cdbbe0d8a38bd683fb860d7e12cb9becdd1bf6 0.600000000000 1643472 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": 1157859, "vin": [ { "gen": { "height": 1157849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e1249f0a06608a69b2a198c1cdbbe0d8a38bd683fb860d7e12cb9becdd1bf6" } } ], "extra": [ 1, 20, 151, 187, 221, 122, 3, 185, 4, 122, 29, 99, 215, 51, 55, 81, 119, 89, 117, 177, 129, 67, 208, 90, 5, 197, 208, 53, 164, 86, 56, 22, 161, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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