Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49097394675ec8eeb8e803cb8c7232234d6e4c782f272489888f270499ff942

Tx prefix hash: 842a4e9fdbd29f1321d6f8c0541e104390c3e6cf4f7647bc0c1f337e694bbafa
Tx public key: df67c35a6b3d3e453e24efdfb4fc1a3cc025a1b2e5715e76889a556132b4871c
Timestamp: 1578082609 Timestamp [UCT]: 2020-01-03 20:16:49 Age [y:d:h:m:s]: 05:030:21:27:54
Block: 37966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171973 RingCT/type: yes/0
Extra: 01df67c35a6b3d3e453e24efdfb4fc1a3cc025a1b2e5715e76889a556132b4871c021100000013d81c26c0000000000000000000

1 output(s) for total of 459.413478061000 dcy

stealth address amount amount idx
00: 59af6180caa9240d909c8238b28e18bd41ba75bfb2e1db104610ec19bfea6cce 459.413478061000 64567 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": 37976, "vin": [ { "gen": { "height": 37966 } } ], "vout": [ { "amount": 459413478061, "target": { "key": "59af6180caa9240d909c8238b28e18bd41ba75bfb2e1db104610ec19bfea6cce" } } ], "extra": [ 1, 223, 103, 195, 90, 107, 61, 62, 69, 62, 36, 239, 223, 180, 252, 26, 60, 192, 37, 161, 178, 229, 113, 94, 118, 136, 154, 85, 97, 50, 180, 135, 28, 2, 17, 0, 0, 0, 19, 216, 28, 38, 192, 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