Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df944266d4e2caca4dc5cdd0cc245a7e359915f4dc691854ad1c0e16d8566f4

Tx prefix hash: bca059646d7cddfec502e209092514cc3d5e63f796c1ee4b9077839611062015
Tx public key: 5973713a3c2f0be821450cef2a30d8fde595792543f764bf319b50eb1bdbcb0a
Timestamp: 1737934086 Timestamp [UCT]: 2025-01-26 23:28:06 Age [y:d:h:m:s]: 00:141:06:48:37
Block: 1205912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100850 RingCT/type: yes/0
Extra: 015973713a3c2f0be821450cef2a30d8fde595792543f764bf319b50eb1bdbcb0a021100000017007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706b3f835cdbe66ab13195dd2b538078f31de3c9d8d31f5634489f65f92a5c91 0.600000000000 1692611 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": 1205922, "vin": [ { "gen": { "height": 1205912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706b3f835cdbe66ab13195dd2b538078f31de3c9d8d31f5634489f65f92a5c91" } } ], "extra": [ 1, 89, 115, 113, 58, 60, 47, 11, 232, 33, 69, 12, 239, 42, 48, 216, 253, 229, 149, 121, 37, 67, 247, 100, 191, 49, 155, 80, 235, 27, 219, 203, 10, 2, 17, 0, 0, 0, 23, 0, 127, 151, 138, 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