Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bfa26ebe6e41cf055a7baefa97992cdaa94b54fd4656b553c3b03557b3c2208

Tx prefix hash: de3dca17c9583aa6b0110ddc1186f5a43da148778d57f5116afe49d20bfafdf6
Tx public key: 1fdb6631a9e694039fd2fc8504092ecc4a7c072ed4ffd6d55a77641a1e22726e
Timestamp: 1721497926 Timestamp [UCT]: 2024-07-20 17:52:06 Age [y:d:h:m:s]: 00:191:01:24:50
Block: 1069970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136461 RingCT/type: yes/0
Extra: 011fdb6631a9e694039fd2fc8504092ecc4a7c072ed4ffd6d55a77641a1e22726e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a2257b9f6ad4d378e88887391b892bae69d0c6ed4318214c37fe1c39326b89 0.600000000000 1541611 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": 1069980, "vin": [ { "gen": { "height": 1069970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a2257b9f6ad4d378e88887391b892bae69d0c6ed4318214c37fe1c39326b89" } } ], "extra": [ 1, 31, 219, 102, 49, 169, 230, 148, 3, 159, 210, 252, 133, 4, 9, 46, 204, 74, 124, 7, 46, 212, 255, 214, 213, 90, 119, 100, 26, 30, 34, 114, 110, 2, 17, 0, 0, 0, 5, 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