Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 485a2492c8da539f7b519f8471df8cbb1886d0ddf883f52cfbccdd43dcc74820

Tx prefix hash: f8ff41717b9444d7a7f2c84f6a63d17700e632c7946aa9d825d96b008a70a1ba
Tx public key: 2a9e9d8f2cf464c818d83d916566dcafb20eff222e0a4984eae10c07e6d0d09e
Timestamp: 1712726729 Timestamp [UCT]: 2024-04-10 05:25:29 Age [y:d:h:m:s]: 00:232:14:58:47
Block: 997232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166559 RingCT/type: yes/0
Extra: 012a9e9d8f2cf464c818d83d916566dcafb20eff222e0a4984eae10c07e6d0d09e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a9c060776915484b89c07da02d003b35f0b3894cf2c8bd16c973614a77c21fb 0.600000000000 1457662 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": 997242, "vin": [ { "gen": { "height": 997232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a9c060776915484b89c07da02d003b35f0b3894cf2c8bd16c973614a77c21fb" } } ], "extra": [ 1, 42, 158, 157, 143, 44, 244, 100, 200, 24, 216, 61, 145, 101, 102, 220, 175, 178, 14, 255, 34, 46, 10, 73, 132, 234, 225, 12, 7, 230, 208, 208, 158, 2, 17, 0, 0, 0, 5, 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