Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1607261c21f23eecccb8a8ae855abb1b294f4ee19be783c2a4673058dbb29330

Tx prefix hash: c3f9d85124b7586ee0564f20a23a936cbb16a8ac4aa4e5770c2ada3728f0bda9
Tx public key: e6493625227976a34dbe2273e9420bfe900c6c7a1a5738afd265e9659b23a60d
Timestamp: 1716067129 Timestamp [UCT]: 2024-05-18 21:18:49 Age [y:d:h:m:s]: 00:238:04:45:05
Block: 1024950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170475 RingCT/type: yes/0
Extra: 01e6493625227976a34dbe2273e9420bfe900c6c7a1a5738afd265e9659b23a60d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3130f13a6de05a4d673b280caef5c0e3b3d3c52ba44e7d5c52fccd195e1e7be7 0.600000000000 1491093 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": 1024960, "vin": [ { "gen": { "height": 1024950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3130f13a6de05a4d673b280caef5c0e3b3d3c52ba44e7d5c52fccd195e1e7be7" } } ], "extra": [ 1, 230, 73, 54, 37, 34, 121, 118, 163, 77, 190, 34, 115, 233, 66, 11, 254, 144, 12, 108, 122, 26, 87, 56, 175, 210, 101, 233, 101, 155, 35, 166, 13, 2, 17, 0, 0, 0, 5, 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