Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b875703647674cfe16ce235058bac388d38818ddb8bd2256d06dc2a9beecaa

Tx prefix hash: 80f549795f4f2d5d58f8859bf2725c0bda6bed6e595dc5fc1dbb4fed1db4455a
Tx public key: a384ee89a7e90e4c35d2681038b7f40d4a7147371df457d5c38068bc36e72d2a
Timestamp: 1709907970 Timestamp [UCT]: 2024-03-08 14:26:10 Age [y:d:h:m:s]: 00:327:15:13:59
Block: 973899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234252 RingCT/type: yes/0
Extra: 01a384ee89a7e90e4c35d2681038b7f40d4a7147371df457d5c38068bc36e72d2a02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbdbb869154466643ce58c1c4cd6a96caa7a3da4666aea68a00f3110812d4ed6 0.600000000000 1433842 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": 973909, "vin": [ { "gen": { "height": 973899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbdbb869154466643ce58c1c4cd6a96caa7a3da4666aea68a00f3110812d4ed6" } } ], "extra": [ 1, 163, 132, 238, 137, 167, 233, 14, 76, 53, 210, 104, 16, 56, 183, 244, 13, 74, 113, 71, 55, 29, 244, 87, 213, 195, 128, 104, 188, 54, 231, 45, 42, 2, 17, 0, 0, 0, 14, 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