Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5eca03b9e3dab57e8df6660b0f915006271c1f8117b8a177fd54debe8b676a

Tx prefix hash: 113114fe4fba2107603f31ea58eca0036ebaa0ff7a9b02d8ef1affaef155b4b8
Tx public key: 4f325a1e03618af65a8bec64626e9bee3baba26cc60f2b82d3ca2d0404eb5780
Timestamp: 1705121836 Timestamp [UCT]: 2024-01-13 04:57:16 Age [y:d:h:m:s]: 01:073:07:43:04
Block: 934188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313492 RingCT/type: yes/0
Extra: 014f325a1e03618af65a8bec64626e9bee3baba26cc60f2b82d3ca2d0404eb578002110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2fc467131489d7cd2152b4e1d9ca8e820215fd6c64fdbdd4bad092039275fd3 0.600000000000 1392176 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": 934198, "vin": [ { "gen": { "height": 934188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2fc467131489d7cd2152b4e1d9ca8e820215fd6c64fdbdd4bad092039275fd3" } } ], "extra": [ 1, 79, 50, 90, 30, 3, 97, 138, 246, 90, 139, 236, 100, 98, 110, 155, 238, 59, 171, 162, 108, 198, 15, 43, 130, 211, 202, 45, 4, 4, 235, 87, 128, 2, 17, 0, 0, 0, 12, 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