Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f867c8aa727753c6d9cd4490b4e6605923fbba7396ae39676b3f339fc8727b4b

Tx prefix hash: f4c630b57f8d4fc9dfb634996d609268f843f740d6f83258c4a3bf0319af9623
Tx public key: 44af9b3efa5844392b97e90ce8ec978cbae674e20b649ea5f09d7367a253374f
Timestamp: 1737170946 Timestamp [UCT]: 2025-01-18 03:29:06 Age [y:d:h:m:s]: 00:058:07:41:32
Block: 1199757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41477 RingCT/type: yes/0
Extra: 0144af9b3efa5844392b97e90ce8ec978cbae674e20b649ea5f09d7367a253374f0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeface4cc41c84302fd5e7e8b8bf92e597b49f9303bea9567105436c7d3bb191 0.600000000000 1686390 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": 1199767, "vin": [ { "gen": { "height": 1199757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeface4cc41c84302fd5e7e8b8bf92e597b49f9303bea9567105436c7d3bb191" } } ], "extra": [ 1, 68, 175, 155, 62, 250, 88, 68, 57, 43, 151, 233, 12, 232, 236, 151, 140, 186, 230, 116, 226, 11, 100, 158, 165, 240, 157, 115, 103, 162, 83, 55, 79, 2, 17, 0, 0, 0, 9, 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