Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b24a4b4858d58055914f1ece1d72cf56d82c54a3f14506e17dba987eba45396

Tx prefix hash: 35fc19bc8fd9cc29ce4b9d2193854bcdc69142020c6f761a6d5e2b4a04d6c916
Tx public key: ac0c1180b5b79af2f9a35f592c6be8aa3cd49a457db2f3f7f63d3b7c72e78a1a
Timestamp: 1707144373 Timestamp [UCT]: 2024-02-05 14:46:13 Age [y:d:h:m:s]: 01:023:08:04:06
Block: 950964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277706 RingCT/type: yes/0
Extra: 01ac0c1180b5b79af2f9a35f592c6be8aa3cd49a457db2f3f7f63d3b7c72e78a1a02110000000810a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6ad7857db252277ed7c2b06218ba25fa929558d03577a9b062505084062236 0.600000000000 1409664 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": 950974, "vin": [ { "gen": { "height": 950964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6ad7857db252277ed7c2b06218ba25fa929558d03577a9b062505084062236" } } ], "extra": [ 1, 172, 12, 17, 128, 181, 183, 154, 242, 249, 163, 95, 89, 44, 107, 232, 170, 60, 212, 154, 69, 125, 178, 243, 247, 246, 61, 59, 124, 114, 231, 138, 26, 2, 17, 0, 0, 0, 8, 16, 161, 116, 143, 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