Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8086a2a9182b4670c8401272abff5b74d2546ce88e917fa17c3dcecab9ecdbb4

Tx prefix hash: 45d91139cb6c335c9564f290d5006a5ab1b1b36d02147a13e1f6c7c5ba885a83
Tx public key: 369d297f9a52ebcf23b2abaa79c84c4221444429142d384c3e84ee9518236f52
Timestamp: 1737157276 Timestamp [UCT]: 2025-01-17 23:41:16 Age [y:d:h:m:s]: 00:333:17:00:59
Block: 1199648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236050 RingCT/type: yes/0
Extra: 01369d297f9a52ebcf23b2abaa79c84c4221444429142d384c3e84ee9518236f520211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85cf79e461a0f9a7e018e7aaac76ab41f862afe1b4f873bcd9042458ef4d2a3a 0.600000000000 1686281 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": 1199658, "vin": [ { "gen": { "height": 1199648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85cf79e461a0f9a7e018e7aaac76ab41f862afe1b4f873bcd9042458ef4d2a3a" } } ], "extra": [ 1, 54, 157, 41, 127, 154, 82, 235, 207, 35, 178, 171, 170, 121, 200, 76, 66, 33, 68, 68, 41, 20, 45, 56, 76, 62, 132, 238, 149, 24, 35, 111, 82, 2, 17, 0, 0, 0, 7, 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