Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e21f5da71fcea0ea1d52f929583521c4ccfc46e8a9bb0f553a566093a6c7828

Tx prefix hash: f9f9a99cfa40d04d71fe37cc4580ed5ce4b970ba81a9fa1ad892b466f6a2ea65
Tx public key: 8ad4a84333a2f987665ed7fa27502aaaf2210afb647a678bf009f5bc537ad293
Timestamp: 1720380487 Timestamp [UCT]: 2024-07-07 19:28:07 Age [y:d:h:m:s]: 00:254:23:43:24
Block: 1060710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182191 RingCT/type: yes/0
Extra: 018ad4a84333a2f987665ed7fa27502aaaf2210afb647a678bf009f5bc537ad293021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c358ccaa419c2930e22ea7f9b0d68a2b45eebebbaa9e47d8a2e79a8520a40a7 0.600000000000 1531195 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": 1060720, "vin": [ { "gen": { "height": 1060710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c358ccaa419c2930e22ea7f9b0d68a2b45eebebbaa9e47d8a2e79a8520a40a7" } } ], "extra": [ 1, 138, 212, 168, 67, 51, 162, 249, 135, 102, 94, 215, 250, 39, 80, 42, 170, 242, 33, 10, 251, 100, 122, 103, 139, 240, 9, 245, 188, 83, 122, 210, 147, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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