Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf6527d2eaef172b4639d0629622b2271a02b84d279307723e9efa719a5f7ed

Tx prefix hash: 19f686dd8c7f276bc2aa4d93b5ccfc60acc00efa16cc7c74b2c09d151923e852
Tx public key: 4df75a4a59f9313b738fb677ecf665a40d439e2d5ba0712ac291077371b9669f
Timestamp: 1737254637 Timestamp [UCT]: 2025-01-19 02:43:57 Age [y:d:h:m:s]: 00:056:18:47:44
Block: 1200419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40405 RingCT/type: yes/0
Extra: 014df75a4a59f9313b738fb677ecf665a40d439e2d5ba0712ac291077371b9669f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e00c591b89ff0931a66a5aa5dc6af532104aeb823fd0a16f15662f613642c5ab 0.600000000000 1687062 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": 1200429, "vin": [ { "gen": { "height": 1200419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e00c591b89ff0931a66a5aa5dc6af532104aeb823fd0a16f15662f613642c5ab" } } ], "extra": [ 1, 77, 247, 90, 74, 89, 249, 49, 59, 115, 143, 182, 119, 236, 246, 101, 164, 13, 67, 158, 45, 91, 160, 113, 42, 194, 145, 7, 115, 113, 185, 102, 159, 2, 17, 0, 0, 0, 2, 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