Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff8f820de09b5cd6acf863085f4b9174994fc7adeda64c7bd3d5246c53c16385

Tx prefix hash: e0510231fd9d7f43af69c8471000c5deaf9ceac968ae9178b1e0fbc5533b49dd
Tx public key: f01768caf228b4e65b31b23359d193ea7de9e31576cba7f3f55b1844e44b520c
Timestamp: 1749645462 Timestamp [UCT]: 2025-06-11 12:37:42 Age [y:d:h:m:s]: 00:152:12:35:45
Block: 1302766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106687 RingCT/type: yes/0
Extra: 01f01768caf228b4e65b31b23359d193ea7de9e31576cba7f3f55b1844e44b520c02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0248f12a9ba6bf0f4d99ddd2614b0fd86cf02defbd91b2bc94a3466e7ce5db7 0.600000000000 1790339 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": 1302776, "vin": [ { "gen": { "height": 1302766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0248f12a9ba6bf0f4d99ddd2614b0fd86cf02defbd91b2bc94a3466e7ce5db7" } } ], "extra": [ 1, 240, 23, 104, 202, 242, 40, 180, 230, 91, 49, 178, 51, 89, 209, 147, 234, 125, 233, 227, 21, 118, 203, 167, 243, 245, 91, 24, 68, 228, 75, 82, 12, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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