Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2d7080d5e7f25016c60977b4a472be109410b297a6789124601f7727f91da4

Tx prefix hash: 8f1f1dae959fc0c5946e088980243c5de249227570a6e76bebb732c45192be01
Tx public key: 85ad3e094d78586f3ae9f789c3a4880a9aebabaa3e2436a66f32cbbc792025d4
Timestamp: 1724437596 Timestamp [UCT]: 2024-08-23 18:26:36 Age [y:d:h:m:s]: 00:265:19:55:03
Block: 1094361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189864 RingCT/type: yes/0
Extra: 0185ad3e094d78586f3ae9f789c3a4880a9aebabaa3e2436a66f32cbbc792025d4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f30746f47e893911ab7bda07bfcd353491a946c4fb53691237dce381c0f76e 0.600000000000 1569478 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": 1094371, "vin": [ { "gen": { "height": 1094361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f30746f47e893911ab7bda07bfcd353491a946c4fb53691237dce381c0f76e" } } ], "extra": [ 1, 133, 173, 62, 9, 77, 120, 88, 111, 58, 233, 247, 137, 195, 164, 136, 10, 154, 235, 171, 170, 62, 36, 54, 166, 111, 50, 203, 188, 121, 32, 37, 212, 2, 17, 0, 0, 0, 2, 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