Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b99d946338bf72b8f96d8ffde669695e4bcbb5285b8e84f4aa4de40801ab86

Tx prefix hash: 03fe41ced6031df48df6a1e3daf00a8b4f5b8816f2d47b9d8cec57f6d8bdcab3
Tx public key: 4adeb9c6283079924c87e88ed5a5db6acdc7bd2dc889fd156a674abf36196021
Timestamp: 1737027549 Timestamp [UCT]: 2025-01-16 11:39:09 Age [y:d:h:m:s]: 00:153:06:48:47
Block: 1198572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109251 RingCT/type: yes/0
Extra: 014adeb9c6283079924c87e88ed5a5db6acdc7bd2dc889fd156a674abf361960210211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0995947b924fea5597dab4e232ec5ba29643b1f4722b78722b2e9be2749bfd5 0.600000000000 1685197 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": 1198582, "vin": [ { "gen": { "height": 1198572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0995947b924fea5597dab4e232ec5ba29643b1f4722b78722b2e9be2749bfd5" } } ], "extra": [ 1, 74, 222, 185, 198, 40, 48, 121, 146, 76, 135, 232, 142, 213, 165, 219, 106, 205, 199, 189, 45, 200, 137, 253, 21, 106, 103, 74, 191, 54, 25, 96, 33, 2, 17, 0, 0, 0, 8, 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