Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2baeffdfe960408656135b7ba5b7688df25a99d6a2dafb5dacb08f3b663f10dd

Tx prefix hash: cfc26b0e96981a4237fcbdf9d67e294d2663b9df36806fb7b8117f79349a78f9
Tx public key: afb1e811d4c749c6111e66695fafde667f10c547208068e21880699d3d597dca
Timestamp: 1709849295 Timestamp [UCT]: 2024-03-07 22:08:15 Age [y:d:h:m:s]: 01:081:23:44:10
Block: 973409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319630 RingCT/type: yes/0
Extra: 01afb1e811d4c749c6111e66695fafde667f10c547208068e21880699d3d597dca02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe0b6a5b267eea6b5d4bfcdcc5fb00d79a8e68c691ff660b6625aef9b51648bb 0.600000000000 1433344 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": 973419, "vin": [ { "gen": { "height": 973409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0b6a5b267eea6b5d4bfcdcc5fb00d79a8e68c691ff660b6625aef9b51648bb" } } ], "extra": [ 1, 175, 177, 232, 17, 212, 199, 73, 198, 17, 30, 102, 105, 95, 175, 222, 102, 127, 16, 197, 71, 32, 128, 104, 226, 24, 128, 105, 157, 61, 89, 125, 202, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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