Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f3f6914de81d722d3043f5021784d2e394e23a2e2fc743b7226e82126860f2

Tx prefix hash: ba9bae4ffbf9c8b49a0e900f2c4be6f5073d3368687e8e3e36869b7baa9c0592
Tx public key: ba63e417f44310802de69fbed29f2d3d37f4e32a771dc844a8084c8625d9e5fe
Timestamp: 1730989746 Timestamp [UCT]: 2024-11-07 14:29:06 Age [y:d:h:m:s]: 00:143:23:32:37
Block: 1148580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102728 RingCT/type: yes/0
Extra: 01ba63e417f44310802de69fbed29f2d3d37f4e32a771dc844a8084c8625d9e5fe0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0b528f8936beff63aed48866a5a5c26d4c89b190f7b7930eb442204cfa4038a 0.600000000000 1633461 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": 1148590, "vin": [ { "gen": { "height": 1148580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0b528f8936beff63aed48866a5a5c26d4c89b190f7b7930eb442204cfa4038a" } } ], "extra": [ 1, 186, 99, 228, 23, 244, 67, 16, 128, 45, 230, 159, 190, 210, 159, 45, 61, 55, 244, 227, 42, 119, 29, 200, 68, 168, 8, 76, 134, 37, 217, 229, 254, 2, 17, 0, 0, 0, 2, 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