Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aea9ce71aaa7f31419b33b654fc27e146d83a993c56cb930ea94896070f7944

Tx prefix hash: 5bdc4e2c03f5ff14d5a70592ade5758ca08f83b444d631ef76c830d432114b9a
Tx public key: 652458a8cb4e6953e38c875632c5bca442dc40f746958efdfcd58714db55633d
Timestamp: 1719719097 Timestamp [UCT]: 2024-06-30 03:44:57 Age [y:d:h:m:s]: 00:222:09:06:13
Block: 1055214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158873 RingCT/type: yes/0
Extra: 01652458a8cb4e6953e38c875632c5bca442dc40f746958efdfcd58714db55633d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd56477822aa041880f4ed4a07ebf4b45b8b5bf00a1e4eac35474b7e9c5bdf89 0.600000000000 1525611 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": 1055224, "vin": [ { "gen": { "height": 1055214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd56477822aa041880f4ed4a07ebf4b45b8b5bf00a1e4eac35474b7e9c5bdf89" } } ], "extra": [ 1, 101, 36, 88, 168, 203, 78, 105, 83, 227, 140, 135, 86, 50, 197, 188, 164, 66, 220, 64, 247, 70, 149, 142, 253, 252, 213, 135, 20, 219, 85, 99, 61, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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