Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8348c72b4e971bab2488a563258162da119c3b0028976be6214608240fffef23

Tx prefix hash: 90d5a4f995d1054c77bf1229801649166f5d60338f4b4672f33a6b0d39630cb4
Tx public key: 27b01751460d3a416202750e9dab1e71b7f256ad0277f5b0fb68a2eb3505e532
Timestamp: 1583750130 Timestamp [UCT]: 2020-03-09 10:35:30 Age [y:d:h:m:s]: 04:295:23:39:22
Block: 79035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106617 RingCT/type: yes/0
Extra: 0127b01751460d3a416202750e9dab1e71b7f256ad0277f5b0fb68a2eb3505e5320211000000096d997e00000000000000000000

1 output(s) for total of 335.834282370000 dcy

stealth address amount amount idx
00: 03c51d845d55e085046ed46eeb1a8eb7209814f1c1f39e30a6eb5ff770d4e1f5 335.834282370000 144763 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": 79045, "vin": [ { "gen": { "height": 79035 } } ], "vout": [ { "amount": 335834282370, "target": { "key": "03c51d845d55e085046ed46eeb1a8eb7209814f1c1f39e30a6eb5ff770d4e1f5" } } ], "extra": [ 1, 39, 176, 23, 81, 70, 13, 58, 65, 98, 2, 117, 14, 157, 171, 30, 113, 183, 242, 86, 173, 2, 119, 245, 176, 251, 104, 162, 235, 53, 5, 229, 50, 2, 17, 0, 0, 0, 9, 109, 153, 126, 0, 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