Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6399a248b5ec11e7290f31ba9101f9ee02016993b123dc4f7c601732c698ea17

Tx prefix hash: d0fc2f8a891de08b5599c8993adf0e01e5bd7385562a28e4d84f017440bbf5a4
Tx public key: 7dfbb7bdf0bca54af025b7b3f2fc56e9faf63e786e5771f55b2c268acc502eb3
Timestamp: 1725800715 Timestamp [UCT]: 2024-09-08 13:05:15 Age [y:d:h:m:s]: 00:257:04:46:14
Block: 1105651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183693 RingCT/type: yes/0
Extra: 017dfbb7bdf0bca54af025b7b3f2fc56e9faf63e786e5771f55b2c268acc502eb3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d21e6cf22a3d8c64fe6231d909342f0a7efe4256dbb3651c38cabd85dc7f93a 0.600000000000 1583056 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": 1105661, "vin": [ { "gen": { "height": 1105651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d21e6cf22a3d8c64fe6231d909342f0a7efe4256dbb3651c38cabd85dc7f93a" } } ], "extra": [ 1, 125, 251, 183, 189, 240, 188, 165, 74, 240, 37, 183, 179, 242, 252, 86, 233, 250, 246, 62, 120, 110, 87, 113, 245, 91, 44, 38, 138, 204, 80, 46, 179, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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