Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38df94f40b142fcffed84ad0a02567e513bd088790aeb6aceb7c9c0ebf4a0d21

Tx prefix hash: ba62a800743659c1b3046c0c4149ecc519fffda72298eab6c6539818982be086
Tx public key: 3f76c55af5914e9d9868dd6f04a3ced6044a69fea7cd62db69fa07bf9d6af517
Timestamp: 1639149516 Timestamp [UCT]: 2021-12-10 15:18:36 Age [y:d:h:m:s]: 03:171:00:01:10
Block: 392573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 900988 RingCT/type: yes/0
Extra: 013f76c55af5914e9d9868dd6f04a3ced6044a69fea7cd62db69fa07bf9d6af517021100000020e9564d6f000000000000000000

1 output(s) for total of 30.707400161000 dcy

stealth address amount amount idx
00: 1bf5a6a66e5fd6d57f41187f42a827a90ea9958bf6313f199af0d6443a7cf4cd 30.707400161000 789498 of 0

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": 392583, "vin": [ { "gen": { "height": 392573 } } ], "vout": [ { "amount": 30707400161, "target": { "key": "1bf5a6a66e5fd6d57f41187f42a827a90ea9958bf6313f199af0d6443a7cf4cd" } } ], "extra": [ 1, 63, 118, 197, 90, 245, 145, 78, 157, 152, 104, 221, 111, 4, 163, 206, 214, 4, 74, 105, 254, 167, 205, 98, 219, 105, 250, 7, 191, 157, 106, 245, 23, 2, 17, 0, 0, 0, 32, 233, 86, 77, 111, 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